Overview 

 The Apple MIDI Manager passes MIDI messages into Flypaper's MIDI Manager Input Ports (which have been connected in Patchbay).  All MIDI Messages are recorded into the Session's log, on disk (except in  record mute mode).

   MIDI Messages stored into the Session Log on disk are retrieved as quickly as possible checked against cues in the Session Definitions.  Any matches may also store values from MIDI Messages into user variables.  Incoming high-level Apple Events are also checked against the cues in the Session Definitions.

   If a MIDI Manager message matched a Session Definition's cue, the Session Definition's reaction is invoked.  This may cause an alert dialog, a sound, an output MIDI message, etc.

Flypapers most important task is to store the incoming MIDI information onto the disk (the Session Log).  Then, time permitting, it looks through the MIDI Messages stored on disk to look for Session Definition cue matches.  You may notice a significant lag in controller sliders and keyboards while using Flypaper.  There are several techniques you can use to minimize the lag between a MIDI Message and a Flypaper reaction.

• Responses take time, including the Blinking of Session Cues option, the Autofront option, and the Autoscroll option.

• More Session Definitions take longer to search through on each incoming MIDI Message
• Store your Session Documents on a RAM disk for improved performance.
• Catch up when you fall behind recognizing cues by issuing the "Reset/All Notes Off" command from the Options menu.